feat: register Ripple in community catalog#2272
feat: register Ripple in community catalog#2272chordpli wants to merge 3 commits intogithub:mainfrom
Conversation
- Extension ID: ripple - Version: 1.0.0 - Author: chordpli - 3 commands (scan, resolve, check), 1 hook (after_implement) - Delta-anchored side effect detection across 9 domain-agnostic categories
chordpli
changed the title
There was a problem hiding this comment.
Pull request overview
Adds the Ripple community extension to Spec Kit’s community catalog and surfaces it in the main README’s Community Extensions table.
Changes:
- Bumps the community catalog’s top-level
updated_attimestamp. - Adds a new
rippleentry toextensions/catalog.community.jsonwith metadata (download URL, docs, tags, requirements, etc.). - Adds a corresponding “Ripple” row to the Community Extensions table in
README.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| extensions/catalog.community.json | Adds the Ripple extension entry and updates the catalog timestamp. |
| README.md | Adds Ripple to the Community Extensions table. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Moved ripple catalog entry from between reconcile/refine to between review/security-review. Updated README table order to match.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Additional Context: How Ripple Complements Existing ExtensionsThree post-implementation extensions share the
All findings are delta-anchored: they must pass a causation test. Pre-existing issues and design flaws stay with When tested on the same implementation:
Ripple also detects fix-induced side effects: the See Complementary Perspectives in the README for the full comparison. |
Extension Submission
Extension Name: Ripple
Extension ID: ripple
Version: 1.0.0
Author: chordpli
Repository: https://github.com/chordpli/spec-kit-ripple
Motivation
After implementation, tests verify intended behavior — but they're rarely designed to detect what a change does to code outside the change set. Ripple was created to address this gap: detecting side effects caused by changes you just made, within the scope of those changes.
How It Differs from Existing Extensions
review,staff-review)How It Works
scancompares the implementation against the baseline (git merge-base) and analyzes across 9 domain-agnostic categories (Data Flow, State & Lifecycle, Interface Contract, Resource & Performance, Concurrency, Distributed Coordination, Configuration & Environment, Error Propagation, Observability). Every finding must pass a causation test: "If this implementation had not been made, would this problem exist?" If yes, it's a pre-existing issue and excluded from the report.resolvewas inspired by/speckit.clarify. Each side effect can be fixed in multiple ways with different tradeoffs. For each finding, it presents 2-4 concrete fix strategies (e.g., minimal patch, structural refactor, defer to next release) and asks: "How do you want to fix this, and what outcome do you expect?" Decisions are recorded inripple-report.mdand implementation guidance is saved toripple-fixes.md— ready for/speckit.implementto consume.checkre-verifies findings after fixes are applied and detects fix-induced side effects — new problems created by the fixes themselves. This creates a feedback loop: fixes may introduce new risks, which check catches before the next iteration. Real-world testing showed convergence from 3 CRITICAL → 1 CRITICAL → 0 CRITICAL, with each check cycle surfacing issues introduced by previous fixes.Hook:
after_implement— prompts to scan after implementation completes.Checklist
Testing